Self-driven and adaptable multi-vbng management orchestration

ABSTRACT

A broadband network gateway (BNG) controller is described that includes a network subscriber database (NSDB) and one or more core applications. The NSDB is configured to store vBNG instance information for one or more subscriber devices. The vBNG instance information specifies vBNG instances operable by one or more edge routers. The vBNG instances are configured to receive requests to access service provider services from the one or more subscriber devices and to selectively authenticate the one or more subscriber devices for network services based on authentication information included in the requests to access services provider services. The one or more core applications include a network instance and configuration manager (NICM). The NICM is configured to modify the vBNG instance information at the NSDB to include an additional vBNG instance and to output, to an edge router, an instruction to generate the additional vBNG instance at the edge router.

This application is a divisional of U.S. application Ser. No. 15/890,589filed Feb. 7, 2018, the entire content of which is herein incorporatedby reference.

TECHNICAL FIELD

The invention relates to computer networks and, more specifically, toimproving an operation of edge routers operating as broadband networkgateways.

BACKGROUND

Large-scale applications geographically distributed over large areasoften process large distributed datasets that require massive datatransfer over a wide area network. Service provider networks typicallyprovide an extensive network infrastructure to support packet-based dataservices offered for use by subscribers. The network infrastructuretypically includes a vast collection of broadband network gateways(BNGs) that facilitate subscriber access to a wide area network (e.g.,the Internet). These BNGs, which may also be referred to as “accessdevices,” may execute various protocols and exchange signaling messagesto anchor and manage subscriber sessions and communication flowsassociated with the subscribers.

SUMMARY

In general, techniques are described for enabling a consolidatedself-driven deployment of “virtual” broadband network gateways (vBNGs).Rather than provisioning a physical BNG for each access point of a widearea network, a service provider network may include a self-driven BNGcontroller that elastically provisions vBNG instances to satisfysubscriber demand. For example, the BNG controller may increase a numberof vBNG instances provisioned on edge routers of a wide area networkwhen existing vBNG instances have reached or are approaching asubscriber capacity. After increasing the number of vBNG instancesprovisioned on the edge routers, the BNG controller may load balance thevBNG instances. In this way, edge routers may be dynamically configuredwith vBNG instances without user intervention.

In some examples, a BNG controller manages BNG instances (e.g.,physical, virtual, etc.). These vBNG instances may manage subscriberlogins for network subscribers and may terminate network subscribers bythe authenticating to provide subscriber services such as, but notlimited to, for example, Internet connection, a firewall, a class ofservice (CoS), or another subscriber service. The BNG controller mayinclude a memory, one or more processors in communication with thememory, a network subscriber database (NSDB), and one or more coreapplications. The NSDB is configured to store vBNG instance informationfor one or more subscriber devices and one or more vBNG instanceinformation. The vBNG instance information specifies a plurality of vBNGinstances operable by one or more edge routers. The plurality of vBNGinstances are configured to receive requests to access service providerservices from the one or more subscriber devices and to selectivelyauthenticate the one or more subscriber devices based on authenticationinformation included in the requests to access services providerservices. The one or more core applications are operable by the one ormore processors. The one or more core applications include a networkinstance and configuration manager (NICM) configured to modify the vBNGinstance information to include an additional vBNG instance to be addedto the plurality of vBNG instances and to output, to an edge router ofthe one or more edge routers, an instruction to generate the additionalvBNG instance at the edge router.

In some examples, a method for managing subscriber logins for networksubscribers includes storing, by one or more NSDB of a BNG controller,vBNG instance information for one or more subscriber devices, the vBNGinstance information specifying a plurality of vBNG instances operableby one or more edge routers. The plurality of vBNG instances areconfigured to receive requests to access service provider services fromthe one or more subscriber devices and to selectively authenticate theone or more subscriber devices based on authentication informationincluded in the requests to access services provider services. Themethod includes modifying, by a NICM operable by one or more processorsof the BNG controller, the vBNG instance information to include anadditional vBNG instance to be added to the plurality of vBNG instancesand outputting, by the NICM, to an edge router of the one or more edgerouters, an instruction to generate the additional vBNG instance at theedge router.

In some examples, an edge router includes a memory, one or moreprocessors in communication with the memory, a BNG virtual machinemanager, and one or more vBNG instances. The BNG virtual machine manageris operable by the one or more processors and configured to receive,from a BNG controller, an instruction to generate a vBNG instance and,in response to the instruction, generate the vBNG instance to provisionone or more vBNG instances at the edge router. The one or more vBNGinstances are operable by the one or more processors and configured toreceive a request to access service provider services from one or moresubscriber devices, and selectively authenticate the one or moresubscriber devices based on authentication information included in therequests to access services provider services.

In some examples, a method includes receiving, by a BNG virtual machinemanager operable by one or more processors of an edge router, from a BNGcontroller, an instruction to generate a vBNG instance and generating,by the BNG virtual machine manager, the vBNG instance at the edge routerto provision one or more vBNG instances operable by the one or moreprocessors in response to the instruction. The method further includesreceiving, by the one or more vBNG instances operable by the one or moreprocessors, a request to access service provider services from one ormore subscriber devices and selectively authenticating, by the one ormore vBNG instances, the one or more subscriber devices based onauthentication information included in the requests to access servicesprovider services.

The details of one or more aspects of the techniques are set forth inthe accompanying drawings and the description below. Other features,objects, and advantages of the techniques will be apparent from thedescription and drawings, and from the claims.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram illustrating an example network system inaccordance with techniques described herein.

FIG. 2 is a block diagram illustrating an example broadband networkgateway (BNG) controller in accordance with techniques described herein.

FIG. 3 is a sequence diagram illustrating an example network resourcemonitoring process in accordance with techniques described herein.

FIG. 4 is a sequence diagram illustrating an example network loadbalancing process in accordance with techniques described herein.

FIG. 5 is a sequence diagram illustrating an example dynamic highavailability process in accordance with techniques described herein.

FIG. 6 is a flowchart illustrating an example mode of operation of a BNGcontroller in accordance with techniques described herein.

FIG. 7 is a flowchart illustrating an example mode of operation of anedge router in accordance with techniques described herein.

DETAILED DESCRIPTION

The virtualized broadband network gateway (vBNG) may be an importantnetwork function for network operators and service providers (SPs)offering retail and wholesale services as a cloud deployment. As usedherein, cloud may refer to a group of networked elements that provideservices, more specifically, for example, a group of networked elementsthat share computational resources for processing tasks of multipleusers. The vBNG may enable a fast rollout of new services and a newcapacity in centralized data centers (DC) or near central office (CO).

The vBNG may be applicable when service providers deploy a distributedarchitecture with a large number of micro data centers near an edge oftheir network. Decentralized network designs may facilitate deploymentof vBNG services and functions in a cost effective manner and close tothe network edge. Depending on the scale required, customers may choosebetween a physical or virtual deployment.

In order to provide cloud based service delivery, some systems may use avBNG, which is a virtualized network function (VNF) for subscribermanagement and services at the edge. Deployment of vBNGs may allownetwork service providers to elastically scale capacity in distributededge or centralized data centers.

Scaling numbers and call setup rate (CSR) for vBNG may be significantlyless compared to the physical BNGs. Customers may deploy multiple vBNGinstances to achieve intended scale. However, there is a need to managethe vBNG instances due, in part, to less capacity. As a number of vBNGinstances grows, so does the difficulty in managing the larger number ofvBNGs.

Service providers deploying vBNGs frequently face challenges especiallywith respect to scale and call setup rate for a single vBNG. Serviceproviders face challenges to manually deploy additional vBNG in order tomeet the requirements and manage so many vBNG instances in the cloud.Usually, there is no compounding of vBNGs or communication betweenvBNGs. Further, physical BNGs and vBNGs may result in security issues,which is important to service providers. Such security issues may bedifficult to manage by systems that use numerous distributed vBNGs.

Because, in some systems, all the vBNG instances are owned by theservice provider, one or more techniques described herein may utilizethe elasticity of the vBNG. This disclosure describes an applicationsuite, which may be deployed in the cloud as a software as a service(SaaS) model. This application suite may manage multiple vBNG instancesin the cloud and interact to present as one consolidated vBNG. Thisconsolidated vBNG may allow for flexibility in terms of expanding andcontracting dynamically in response to evolving network conditions. Oneor more techniques described herein may offer automation to providedifferent services like managing multiple vBNG instances, centralizedsubscriber database, load balancing, high availability, subscriberanalytics, unified security management, configuration management, andother benefits that potentially improve operation of the network itself.

One or more techniques described herein may provide an end-to-endsolution for deployment, expansion, growth and management of a BNGnetwork (including one or both of physical BNGs and vBNG instances (alsoreferred to a “BNG instances”), in the form of one or more applicationswhich can be deployed in the cloud (referring generally to networkprovided services managed and maintained by the service providernetwork). One or more techniques described herein may reduce costs forservice providers, as management may be centralized thereby saving costsassociating with on-site management of a distributed network of physicalBNGs.

FIG. 1 is a block diagram illustrating an example network system 10 inaccordance with techniques described herein. As shown in the example ofFIG. 1, network system 10 includes a service provider network 20 coupledto a public network 22. Service provider network 20 operates as aprivate network that provides packet-based network services tosubscriber devices 18A, 18B, 18C (collectively, “subscriber devices18”).

The elements of network system 10 may support any one or more of avariety of protocols, such as Internet Protocol (IP), Frame Relay,Asynchronous Transfer Mode (ATM), Ethernet, Point-to-Point Protocol(PPP), Point-to-Point Protocol over Ethernet (PPPoE), GPRS tunnelingprotocol (GTP), Dynamic Host Configuration Protocol (DHCP), Layer 2Tunneling Protocol (L2TP), and virtual local area network (VLAN)-relatedprotocols, among others. Using any one or more of these protocols, anyof subscriber devices 18 may present authentication credentials to edgerouters 30-32 to request access to a service provider network 20service. For example, subscriber device 18A may broadcast credentials,such as a username and password, to edge router 30 to request access toa service provided by service provider network 20. Subscriber devices 18may broadcast credentials using, for instance, a PPPoE Active DiscoveryInitiation (PADI) packet to edge routers 30-32.

Service provider network 20 supports one or more packet-based servicesthat are available for request and use by subscriber devices 18. Asexamples, service provider network 20 may provide Internet access, bulkdata delivery, voice over Internet protocol (VoIP), Internet protocoltelevision (IPTV), short messaging service (SMS), wireless applicationprotocol (WAP) service, telnet, or customer-specific applicationservices. Service provider network 20 may include, for instance, a localarea network (LAN), a wide area network (WAN), a virtual LAN (VLAN), anenterprise LAN, a layer 3 virtual private network (VPN), an Internetprotocol (IP) intranet operated by a network service provider that alsooperates access aggregation network 24, an enterprise IP network, orsome combination thereof. In various examples, service provider network20 may be connected to or form part of one or more of a public WAN, theInternet, or to other networks. Service provider network 20 executes oneor more packet data protocols (PDPs), such as IP (IPv4 and/or IPv6),X.25 or point-to-point protocol (PPP), to enable packet-based transportof service provider network 20 services.

Subscriber devices 18A may include, for example, personal computers,laptop computers and/or other types of computing device associated withsubscribers. Subscriber devices 18B may comprise, for example, mobiletelephones, laptop or desktop computers having, e.g., a 3G wirelesscard, wireless-capable netbooks, video game devices, pagers, smartphones, personal data assistants (PDAs) or the like. Subscriber devices18C may include, for example, a workstation, desktop computer, servercomputer, server farm, server cluster, or any other device or group ofdevices that are capable of accessing a computer network via a wirelessand/or wired connection. Each of subscriber devices 18 may be associatedwith a subscriber (e.g., a human, an enterprise, etc.). Applicationsthat access services provided by service provider network 20 mayalternatively be referred to as “user agents.” In this example, any ofsubscriber devices 18 may connect to at least one of edge routers 30-32in order to access service provider network 20.

Edge routers (ERs) 30-32 operate at the borders of aggregation network24 and, responsive to controller 55, apply network services, such asauthorization, policy provisioning, and network connectivity, to networktraffic associated with subscriber devices 18 in communication with edgerouters 30-32. Edge routers 30-32 may include one or more processors(not shown in FIG. 1 and which may include a central processingunit—CPU) that execute software instructions, such as those used todefine a software or computer program, stored to a computer-readablestorage medium (again, not shown in FIG. 1), such as non-transitorycomputer-readable mediums including a storage device (e.g., a diskdrive, or an optical drive) or a memory (such as Flash memory or randomaccess memory (RAM)) or any other type of volatile or non-volatilememory, that stores instructions to cause the one or more processors toperform the techniques described herein. In some examples, edge routers30-32 may comprise a processor in the form of dedicated hardware, suchas one or more integrated circuits, one or more Application SpecificIntegrated Circuits (ASICs), one or more Application Specific SpecialProcessors (ASSPs), one or more Field Programmable Gate Arrays (FPGAs),or any combination of one or more of the foregoing examples of dedicatedhardware, for performing the techniques described herein. Although FIG.1 illustrates one edge router 30, as discussed further in FIG. 2, edgerouter 30 may represent any quantity of edge routers. Similarly, edgerouter 31 may represent any quantity of edge routers.

In the example of FIG. 1, for ease of explanation, service providernetwork 20 is shown having three edge routers 30-32, although theservice provider network may typically service thousands or tens ofthousands of edge routers. For example, edge router 30 may represent amobile gateway, for example, a gateway general packet radio service(GPRS) serving node (GGSN), an access gateway (aGW), or a packet gateway(P-GW). Edge routers 30-32 may include a plurality of service virtualLANs (SVLANs) that partition elements of access network (e.g., DSLAMs)into logically different networks. Different subscriber devices 18 maytherefore connect to edge routers 30-32 using different SVLANs.

As shown in FIG. 1, service provider network 20 may provide subscriberdevices 18B with access to aggregation network 24 via radio signals. Forexample, edge router 30 may be connected to one or more wireless radiosor base stations to wirelessly exchange packetized data with subscriberdevices 18B. The packetized data may then be communicated throughaggregation network 24 of the service provider and ultimately to publicnetwork 22.

Aggregation network 24 provides session management, mobility management,and transport services to support access, by subscriber devices 18, topublic network 22. Edge routers 30-32 provide an anchor point of activesessions for subscriber devices 18. Edge routers 30-32 may maintainsession data and operate as a termination point for communicationsessions established with subscriber devices 18 that are currentlyaccessing packet-based services of public network 22 via aggregationnetwork 24.

Aggregation network 24 provides transport services for network trafficassociated with subscriber devices 18. Aggregation network 24 mayinclude internal routers and switches that provide transport servicesbetween edge routers 30-32. After authentication and establishment ofnetwork access through edge routers 30-32, any one of subscriber devices18 may begin exchanging data packets with public network 22 with suchpackets traversing aggregation network 24. Although not shown,aggregation network may include devices to provide security services,load balancing, billing, deep-packet inspection (DPI), and otherservices for mobile traffic traversing aggregation network 24.

Aggregation network 24 may, for example, include one or more networkdevices (e.g., aggregation nodes) configured to operate as labelswitched routers (LSRs) that forward traffic along transport labelswitched paths (LSPs) defined within aggregation network 24. Edgerouters 30-32 may operate as endpoints for the LSPs to map subscribertraffic into and out of the LSPs. For example, edge routers 30-32 maymap network services to individual LSPs within aggregation network 24.In the example of FIG. 1, controller 55 includes Software DefinedNetwork (SDN) controller 40, which traffic engineers the LSPs throughaggregation network 24 according to the bandwidth, quality of Service(QoS) and availability requirements of network services applications, asfurther described below. In some examples, SDN controller 40 may beomitted.

In the example of FIG. 1, controller 55 includes a BNG controller 35that elastically provisions one or more vBNG instances 57 on edge router30 and/or one or more vBNG instances 61 on edge router 31 to satisfysubscriber demand from subscriber devices 18. Controller 55 may includeone or more processors (not shown in FIG. 1 and which may refer to, asone example, a central processing unit—CPU) that execute softwareinstructions, such as those used to define a software or computerprogram, stored to a computer-readable storage medium (again, not shownin FIG. 1), such as non-transitory computer-readable mediums including astorage device (e.g., a disk drive, or an optical drive) or a memory(such as Flash memory or random access memory (RAM)) or any other typeof volatile or non-volatile memory, that stores instructions to causethe one or more processors to perform the techniques described herein.In some examples, controller 55 may comprise a processor in the form ofa dedicated hardware, such as one or more integrated circuits, one ormore Application Specific Integrated Circuits (ASICs), one or moreApplication Specific Special Processors (ASSPs), one or more FieldProgrammable Gate Arrays (FPGAs), or any combination of one or more ofthe foregoing examples of dedicated hardware, for performing thetechniques described herein.

As used herein, a vBNG instance may refer to software configured on adevice or component (e.g., board or service card) that provides accessto service provider network 20. A vBNG instance may also be referred toas a “virtual BNG” (“vBNG”) or a “vBNG instance.” For example, a vBNGinstance may represent and/or incorporate a software instanceprovisioned on a network access server to provide dial-up or virtualprivate network (VPN) services to an enterprise LAN, a remote accessserver (e.g., broadband remote access server) or broadband servicesrouter that aggregates outputs from one or more digital subscriber lineaccess multiplexers (DSLAMs) into a higher-speed uplink to serviceprovider network 20, a wireless access point (WAP) providing wirelessphysical layer access to service provider network 20, or switches thatuse other LAN-based (e.g., Ethernet) technologies to provide wiredphysical layer access to service provider network 20.

A vBNG instance may manage authentication, authorization, and accounting(AAA) functionality for networks that offer services to one or moresubscribers. The protocol most commonly used by the servers tocommunicate with clients is the remote authentication dial in userservice (RADIUS) protocol. The RADIUS protocol is described in CarlRigney et al., “Remote Authentication Dial In User Server (RADIUS),”Network Working Group of the Internet Engineering Task Force (IETF),Request for Comments 2865, June 2000, which is incorporated by referenceherein in its entirety (referred to hereinafter as “RFC 2865”).Additionally, a vBNG instance may terminate network subscribers byauthenticating to provide subscriber services such as, but not limitedto, for example, an Internet connection, a firewall, a class of service(CoS), or another subscriber service.

In accordance with one or more techniques described in this disclosure,BNG controller 35 may store vBNG instance information for subscriberdevices 18. The vBNG instance information may indicate vBNG instances(e.g., vBNG instances 57, 61, etc.) operable by one or more edge routers(e.g., edge routers 30-32) and configured to receive requests to accessservice provider services from subscriber devices 18 and authenticaterespective requests to access service provider services (e.g., serviceprovider network 20).

vBNG instances 57 may receive a request to access service providerservices from subscriber devices 18, and authenticate respectiverequests to access service provider services. In this example, vBNGinstances 57 may advertise subscriber information to BNG controller 35.For instance, vBNG instances 57 may increment a login count and send anupdated login count at a predetermined time interval (e.g., every ‘n’seconds). In some instances, vBNG instances 57 may increment inflightinformation (e.g., inflight login, inflight logout, etc.) and sendupdated inflight information at a predetermined time interval (e.g.,every ‘n’ seconds). As used herein, an inflight login may refer tosubscriber logins, service attachments during login, or the like thatare in process by vBNG instances 57. For example, an inflight login mayinclude instances when a subscriber is logging in to authenticate,attach services, and the like. As such, inflight login may refer to atime period between when a subscriber is attempting to login to when thesubscriber has completed a login process. Similarly, an inflight logoutmay refer to subscriber logouts, service detachments, or the like duringlogout that are in process by vBNG instances 57. As such, inflightlogout may refer to a time period between when a subscriber isattempting to logout to when the subscriber has completed a logoutprocess.

BNG controller 35 may recompute load balancing for the plurality of vBNGinstances. In this example, in response to determining that resources(e.g., central processing unit (CPU), queues, resources busy, resourcesfull, etc.) of the vBNG instances 57, 61 are at or near a capacity, BNGcontroller 35 may output, to an edge router (e.g., edge router 30, 31),an instruction to instantiate an additional vBNG instance. That is, forexample, BNG controller 35 may output, to vBNG instances 57 and/or vBNGinstances 61, load balancing credit information. In this example, eachof vBNG instances 57 and/or vBNG instances 61 may receive the loadbalancer information from BNG controller 35. Further, in some examples,BNG controller 35 may balance inflight login/logouts.

Edge router 30 may receive, from BNG controller 35, the instruction togenerate an additional vBNG instance and, in response to theinstruction, generate an additional vBNG instance at edge router 30. BNGcontroller 35 may recompute load balancing for the additional vBNGinstance and the plurality of vBNG instances. In this example, BNGcontroller 35 may output a load balancer credit to the additional vBNGinstance. In this example, edge router 30 may receive, from BNGcontroller 35, load balancing credit information. As such, edge router30 may authenticate requests to access service provider services basedon the load balancing credit information.

In this way, BNG controller 35 and edge router 30 may elasticallyincrease or decrease vBNG instances. Elastically increasing ordecreasing vBNG instances may improve an operation of network system 10.For instance, elastically increasing and decreasing vBNG instances maypermit network system 10 to use less power when a demand for BNGservices is low compared to network systems that do not elasticallyincreases or decrease vBNG instances. In another instance, elasticallyincreasing and decreasing vBNG instances may permit network system 10 tosupport all requested BNG processes when a demand for BNG services ishigh compared to network systems that do not elastically increases ordecrease vBNG instances. Although the above examples use edge router 30as a BNG, other examples may use edge router 31 as a BNG.

FIG. 2 is a block diagram illustrating an example BNG controller 35 inaccordance with techniques described herein. BNG controller 35 andoptionally SDN controller 40 may be implemented as controller 55, whichmay be implemented on one or more devices running in a cloud (which is anetwork of the one or more devices that operate in support of thecontroller 55 services described below in more detail). For example, BNGcontroller 35 may be implemented in one or more applications executed ata centralized computing device (e.g., a computer, server, laptop, etc.).In some examples, BNG controller 35 may be implemented in one or moreapplications executed at a plurality of networked computing elements(e.g., a cloud, server cluster, etc.).

Edge routers 30A-30N (collectively, “one or more edge routers 30” orsimply “edge router 30”) may include any suitable number of virtual BNG(vBNG) instances. For example, edge router 30A may include virtual vBNGinstances (vBNG) 57A-vBNG 57N (collectively, vBNG instances 57).Additionally, edge router 30A may include BNG virtual machine manager 59configured to provision (or, in other words, activate) one or more ofvBNG instances 57 and/or to delete (or, in other words, deactivate) oneor more of vBNG instances 57. For instance, edge router 30A may includea hypervisor or virtual machine monitor (VMM) or virtual machine manager(VMM) configured to provision (or, in other words, activate) one or moreof vBNG instances 57 and/or to delete (or, in other words, deactivate)one or more of vBNG instances 57. Similarly, edge router 30N may includevirtual vBNG instances (vBNG) 58A-vBNG 58N (collectively, vBNG instances58). For instance, edge router 30N may include a hypervisor or virtualmachine monitor (VMM) configured to provision (or, in other words,activate) one or more of vBNG instances 58 and/or to delete (or, inother words, deactivate) one or more of vBNG instances 58. Additionally,edge router 30N may include BNG virtual machine manager 65 configured toprovision one or more of vBNG instances 58 and/or to delete one or moreof vBNG instances 58.

In the example of FIG. 2, vBNG instances 57 may be substantially similarto vBNG instances 58 and BNG virtual machine manager 59 is substantiallysimilar to BNG virtual machine manager 65, however, in other examples,vBNG instances 57 and 58 and/or BNG virtual machine managers 59 and 65may be different. Although the example of FIG. 2 illustrates virtualvBNG instances (e.g., vBNG A 57A-vBNG N 57N, vBNG A 58A-vBNG N 58N) asbeing included in edge router 30, in some examples, virtual vBNGinstances may be included in other edge routers of edge routers 30-32.

As shown, BNG controller 35 may include network resource manager (NRM)41 (“NRM 41”), network subscriber database (NSDB) 43 (“NSDB 43”),network instance and configuration manager (NICM) 45 (“NICM 45”),dynamic high availability (DHA) 46 (“DHA 46”), network load balancer(NLB) 47 (“NLB 47”), subscriber analytics (SA) unit 51 (“SA 51”), andunified network security management (USMN) unit 53 (“USMN 53”).

NRM 41 may actively monitor resources across vBNG instances 57 and 58.NRM 41 may monitor both BNG aspects and system resource aspects of eachvBNG instance of vBNG instances 57 and 58. NRM 41 may monitor BNGaspects such as a number of subscribers and services for thesubscribers, IPv4/IPv6 address pools, a usage of IPv4/IPv6 addresspools, quality of service, queues and schedulers, cache (e.g., L1)resources, business services, and/or calls per second (CPS) at each vBNGinstance of vBNG instances 57 and 58. NRM 41 may monitor system resourceaspects such as CPU availability, memory, bandwidth, control packetresponse times, inflight login/logouts (e.g., event rate analyzer),critical management queues, and other system resource aspects. Thus, NRM41 may be “aware” of not only subscriber related resources but alsosystem resources. NRM 41 may also monitor health of each of vBNGinstance of vBNG instances 57 and 58.

NSDB 43 may store a subscriber database for accessing service providernetwork 20. With the access to each of vBNG of vBNG instances 57 and 58,the entire network subscriber database may be maintained at acentralized place. Subscriber databases of individual vBNG instances maybe available at individual vBNG instances. NSDB 43 may have atransaction update mechanism from the individual vBNG subscriberdatabase. NSDB 43 may be in lock-sync with the subscriber database ofindividual vBNG. For example, NSDB 43 and each vBNG of vBNG instances 57and 58 may be configured to synchronize a local database (e.g., memoryof one of edge routers 30-32) of each respective vBNG with NSDB 43.Service providers may have a subscriber database for the entire network(e.g., service provider network 20) at one single place.

With the subscriber data correlation being centralized, BNG controller35 may perform more granular subscriber management, allowing for moredetailed and comprehensive subscriber management compared to subscribermanagement performed with respect to decentralized subscriber data.Subscriber data correlation may be useful and helpful for many newapplications, for example, but not limited to, when one of the vBNGinstances ceases operation. With NSDB 43, BNG controller 35 mayinstantiate a new vBNG instance with little or no delay relative tomanually provisioning a physical BNG, while also potentially recoveringall the subscribers upon provisioning the new vBNG instance. NSDB 43 mayprovide the functionality of vBNG restart. NSDB 43 may include one ormore databases, and may be implemented in a cloud using multiple serverdevices. For example, multiple networked elements may store NSDB 43.

In some examples, NSDB 43 may store subscriber colocation information.For example, a user may log-in at home, then login on a mobile device,and then log-in at an office. By storing subscriber colocationinformation, BNG controller 35 may determine, for example, how much timethe particular user takes to drive between the office and home. BNGcontroller 35 (e.g., NRM 41) may instantiate a new vBNG instance basedon the subscriber colocation information. For instance, NRM 41 mayinstantiate a new vBNG instance to support a subscriber login on amobile device when the particular user drives between the office andhome. In some examples, NSDB 43 may include BNG specific information.Examples of BNG specific information may include, but are not limitedto, for example, subscriber count, inflight logins, inflight logouts,resources, or other BNG specific information.

NICM 45 may create and/or delete a vBNG instance (e.g., vBNG instances57 and 58) as per the need and directive from the NRM 41 and/or NLB 47.Because vBNG instances 57 and 58 may promote a pay as you grow model,customers (e.g., service providers) may optimize cost by instantiatingvBNG instances only when needed and de-instantiating vBNG instancesdynamically. This need-based deployment may reduce the costs associatedwith subscriber management for service providers. Need-based deploymentmay make the network itself (e.g., network system 10) more efficient byreducing needless execution of vBNG processes, saving processor cycles,bandwidth, and memory consumption, which promotes reduced powerconsumption.

In some examples, NICM 45 may create a new vBNG instance when theexisting instances are within a threshold amount of supported subscribercapacity, a login rate is higher than the calls per second (CPS) handledby the existing instances, and/or an existing vBNG instance has ceased.Similarly, when the existing instances are less than a threshold amountof subscriber capacity, and/or a login rate for an existing vBNGinstance is less than a threshold calls per second (CPS), NICM 45 maybring down (or, in other words, delete or deactivate) the particularvBNG and reduce costs for customers. Creating a new vBNG instance ordeactivating existing vBNG instances may improve an operation of anetwork system (e.g., network system 10 of FIG. 1) and is costeffective. For instance, deactivating existing vBNG instances may permitnetwork system 10 to use less power when a demand for BNG services islow compared to network systems that do not elastically increases ordecrease vBNG instances, saving the cost for service providers. Inanother instance, creating a new vBNG instance may permit network system10 to support all requested BNG processes when a demand for BNG servicesis high compared to network systems that do not elastically increases ordecrease vBNG instances.

Regarding the configuration portion of NICM 45, traditionally, somerouter configurations may be applied through a command line interface(CLI), Extensible Markup Language (XML), YAML, or another interface thatrelies on user intervention. However, NICM 45 may maintain configurationtemplates for each of vBNG instance of vBNG instances such that theconfigurations may be replicated automatically without any userintervention. That is, for example, each vBNG instance of vBNG instances57 and 58 may be configured to receive configuration updates from BNGcontroller 35, such as, for example, but not limited to, a configurationtemplate.

Whenever NICM 45 spawns a new vBNG instance, the configuration for thenew vBNG instance may be created from the template and pushed to thevBNG instance. NICM 45 may push and/or publish configuration updates toall vBNG instances without user intervention.

NICM 45 may configure replication policies configured for stanzas suchthat any configuration change learned dynamically from any of the vBNGinstances may be replicated to the remaining vBNG instances, e.g. ifsecurity threat or suspicious flow detected at one of vBNG instance, asolution to the security threat or suspicious flow may be templated andpushed to rest of the vBNG instances without any user intervention.

NLB 47 may load balance vBNG instances 57 and 58. Optimal use ofresources may be possible only when load is balanced at vBNG instances57 and 58. Load balancing on any particular vBNG instance may belimited. In order to effectively balance the load across vBNG instances,NLB 47 may perform load balancing outside the instance, at a centralizedplace like BNG Controller 35. NLB 47 may spread the load of new incomingsubscribers across different vBNG instances. Additionally, oralternatively, NLB 47 may spawn a new vBNG instance if incoming load istoo much to handle. Load balancing outside the instance may make thenetwork itself (e.g., network system 10) more efficient by reducingneedless execution of vBNG processes, saving processor cycles,bandwidth, and memory consumption, which promotes reduced powerconsumption. Thus, NLB 47 may optimize load across the network from acentralized place (e.g., BNG Controller 35) rather than each vBNGoptimizing load at a respective vBNG.

NRM 41 may be aware of subscriber related resource utilization (e.g.number of subscribers, quality of service, queues, IPv4/IPv6 addresspools, a usage of IPv4/IPv6 address pools, loss interference (LI),business services, or other subscriber related resource utilization) aswell as the system resource utilization like (call setup rate, inflightlogin/logouts, CPU, memory, bandwidth, or other system resourceutilization). NRM 41 may balance the load among all the vBNG instances.NRM 41 may divert the load of new incoming subscribers across differentvBNG instances, balancing the load across the entire network. Based onsubscriber related resource utilization, NRM 41 may create the newinstance of vBNG by triggering NICM 45. For instance, NRM 41 may createthe new instance of vBNG by triggering NICM 45 when a number ofsubscribers exceeds a threshold for existing vBNG instances.

Various aspects of the techniques may also provide for Dynamic HighAvailability (DHA). Customers may request high availability (HA) forsubscribers. Deploying two chassis and creating a physical setup may berelatively expensive. Further, a physical setup may be indefinite. Theremay be a need for time-based HA e.g. only during working hours or maynot be needed on weekends. There may be HA needed during maintenancewindow only. Still it's necessary for the customers to purchase theexpensive redundant hardware and deploy permanently. DHA 46 may allowcustomers to configure redundancy policy depending upon their networkrequirement. DHA 46 may dynamically spawn and/or collapse instances ofvBNG together with NICM 45 and configure HA, completely based on theconfigured redundancy policy. For instance, DHA 46 may dynamicallycollapse one or more vBNG instances of vBNG instances 57 and 58. In someexamples, DHA 46 may dynamically spawn one or more additional vBNGinstances to be added to vBNG instances 57 and 58. NICM 45 maydynamically create a new instance of vBNG. When such a need does notexist anymore, NICM 45 may remove the vBNG instance. DHA 46 may make thenetwork itself (e.g., network system 10) more efficient by reducingneedless execution of redundant physical setups, which promotes reducedpower consumption.

NRM 41 may monitor the health of each of the vBNG instances. When NRM 41detects that an instance of vBNG is no longer functioning asprovisioned, NRM 41 may inform NICM 45 to create a new instance of vBNGand restore subscribers with the subscriber data from NSDB 43. As such,NRM 41 may help to provide the functionality of vBNG restart.

SA 51 may collect subscriber data and information for the entirenetwork. Said differently, SA 51 may receive analytics data from atleast one of vBNG instances 57 and 58. In this example, SA 51 maygenerate subscriber behavior data based on the analytics data foroperating vBNG instances 57 and 58. New applications can emerge ifreal-time subscriber data and information for the entire network isavailable in a centralized location. For example, subscriber behaviormay be based on weekends or holidays on a particular part of the worldor subscriber behavior may be based on a sporting event (e.g. superbowl). Based on the analytics collected by SA 51, the service providersmay pre-plan a number of required vBNG instances in a particular datacenter. Additionally, SA 51 may correlate and apply analytics centrallyacross vBNG instances. In some examples, SA 51 may perform machinelearning using data from one vBNG instance and form auto-templates to bedistributed globally to other vBNG instances. Collecting subscriber dataand information for the entire network may make the network itself(e.g., network system 10) more efficient by reducing needless executionof vBNG processes, saving processor cycles, bandwidth, and memoryconsumption, which promotes reduced power consumption.

UNSM 53 may manage network wide distributed denial-of-service (DDoS)detection and protection. In some systems, security is considered onlyat the vBNG instance level. Network-level management of DDoS detectionmay help to truly mitigating the DDoS attack. In the example of FIG. 2,the security of the entire network may be considered at one centralizedplace, for instance, UNSM 53. With the data available for the entirenetwork, UNSM 53 may correlate data for mitigating the DDoS attack. UNSM53 may perform one or more functions of an Intrusion Detection System(IDS) by correlating the security data across the vBNG instances. UNSM53 may identify suspicious flow at the entire network level and mayapply security threat and mitigation techniques across the vBNGinstances. UNSM 53 may identify a security threat from one vBNG instanceand apply mitigation automatically across all vBNG instances. Forexample, UNSM 53 may exchange (e.g., receive and/or output) securityrelated information with each vBNG instance of vBNG instances 57 and 58.

Examples of security related information may include, but are notlimited to, for example: (1) a configuration template indicating asecurity configuration profile which is generated by UNSM 53 to indicateone or more malware programs identified by a physical BNG and/or vBNGthat are to be denied download or open access; (2) a configurationtemplate indicating a security configuration profile which is generatedby UNSM 53 to indicate one or more threatening re-direct sitesidentified by a physical BNG and/or a vBNG that are to be quarantined;(3) a configuration template indicating a security configuration profilewhich is generated by UNSM 53 to indicate one or more sites identifiedby a physical BNG and/or a vBNG to be quarantined; (4) a configurationtemplate indicating a security configuration profile which is generatedby UNSM 53 to indicate ransomeware sites identified by a physical BNGand/or a vBNG to be quarantined; and (5) a configuration templateindicating a security configuration profile which is generated by UNSM53 to indicate traffic that is tapped through LI (Lawful Intercept).Such collected UNSM data may be run through artificial intelligence. Insome examples, such collected UNSM data may be used by data science toidentify criminal activities.

For example, UNSM 53 may receive network security data from vBNGinstances 57 and 58. In this example, UNSM 53 may analyze receivednetwork security data to generate one or more alerts. As used herein,one or more alerts that may be generated by UNSM 53 may refer toinforming a human administrator and/or operator. For example, an alertmay include, a syslog, pop-up, or another alert. In this example, UNSM53 may configure vBNG instances 57 and 58 based on the network securitydata. For instance, UNSM 53 may exchange (e.g., receive and/or output)security related information with each vBNG instance of vBNG instances57 and 58 as discussed above. In some examples, UNSM 53 may output, toeach vBNG instance of vBNG instances 57 and 58, updates. In thisexample, each vBNG instance of vBNG instances 57 and 58 may receiveupdates from UNSM 53 of BNG controller 35.

In accordance with one or more techniques described herein, NSDB 43stores vBNG instance information for one or more subscriber devices. ThevBNG instance information may specify vBNG instances 57 and vBNGinstances 58A-58M. NICM 45 modifies the vBNG instance information toinclude an additional vBNG instance to be added to vBNG instances 57 and58. For example, NICM 45 may add vBNG instance 58N to vBNG instances 57and vBNG instances 58A-58M. NICM 45 outputs an instruction to generatevBNG instance 58N at edge router 30N.

In response to receiving the instruction to generate vBNG instance 58Nat edge router 30N, BNG virtual machine manager 65 generates vBNGinstance 58N at edge router 30N to provision vBNG instances 58. Inresponse to receiving a request to access service provider services fromsubscriber devices 18A and 18B of FIG. 1, vBNG instances 58 mayselectively authenticate subscriber devices 18A and 18B based onauthentication information included in the requests to access servicesprovider services and may provide subscriber services such as, but notlimited to, for example, an Internet connection, a firewall, a class ofservice (CoS), or another subscriber service.

The example of FIG. 2 may provide the following advantages compared tosystems that do not dynamically instantiate vBNG instances. For example,one or more techniques described herein may provide an end-to-endsolution for deployment, expansion, growth and management of edge(network subscribers), in the form of application which can be deployedin cloud. Such techniques may hide the complexity of deployment andday-to-day operations of numerous vBNG instances to a single centralizednode. Such automation may help to remove admin/user intervention, to agreat extent. In some examples, one or more techniques described hereinmay elastically increase/decrease vBNG instances, which may make thenetwork itself (e.g., network system 10) more efficient by reducingneedless execution of vBNG processes, saving processor cycles,bandwidth, and memory consumption, which promotes reduced powerconsumption. In some examples, one or more techniques described hereinmay provide automatic management and compounding solution for multiplevBNG instances. In some examples, one or more techniques describedherein may provide a cost effective approach for service providers. Insome examples, one or more techniques described herein may provide easyto deploy, easy to expand, agility for deploying new services. In someexamples, one or more techniques described herein may provide, due inpart to elasticity, an unlimited amount of scale, call setup rate,and/or resources. In some examples, one or more techniques describedherein may provide an optimal use of resources with load balancingacross the vBNG instances reduces the operational expenses (OPEX), whichmay make the network itself (e.g., network system 10) more efficient byreducing needless execution of vBNG processes, saving processor cycles,bandwidth, and memory consumption, which promotes reduced powerconsumption. In some examples, one or more techniques described hereinmay help to provide no network downtime. In some examples, one or moretechniques described herein may provide automatic recovery of vBNGinstance. In some examples, one or more techniques described herein mayprovide unified security and threat management. In some examples, one ormore techniques described herein may provide intrusion detection andunified suspicious flow detection.

Although FIG. 2 described BNG controller 35 in operation with virtualvBNG instances, in some examples, BNG controller 35 may operate withphysical BNGs or a combination of physical BNGs and virtual vBNGinstances. For example, NRM 41 may actively monitor resources acrossphysical BNGs. In some examples, NLB 47 may load balance physical BNGs.In some examples, NRM 41 may be aware of subscriber related resourceutilization of physical BNGs. In some examples, NRM 41 may monitor thehealth of each physical BNG. In some examples, SA 51 may collectsubscriber data and information for physical BNGs. For example, UNSM 53may manage network wide distributed denial-of-service (DDoS) detectionand protection for physical BNGs.

FIG. 3 is a sequence diagram illustrating an example network resourcemonitoring process in accordance with techniques described herein. FIG.3 illustrates an exemplary use case describing how an “out of resources”condition local to a vBNG is communicated to NRM 41 which could resultin creation of a new vBNG guest instance. FIG. 3 is discussed withrespect to FIG. 1 and FIG. 2 for exemplary purposes only. Client 258 maybe an example of subscriber device 18A of FIG. 1. vBNG N 257 may be anexample of vBNG N 57N of FIG. 2. vBNG M 261 may be an example of vBNG N61N of FIG. 2. NRM 241 may be an example of NRM 41 of FIG. 2. NLB 247may be an example of NLB 47 of FIG. 2. NICM 245 may be an example ofNICM 45 of FIG. 2.

In the example of FIG. 3, all the vBNG instances are running at close tofull capacity. That is, for example, the existing vBNG instances arerunning out of resources and/or the number of subscribers logged in arenearing the capacity of the vBNG instances. In such instances, anadministrator may want to spawn a new instance of vBNG to take up thenew subscribers. In the example of FIG. 3, instead of manually creatingthe guest instance and then adding configuration, BNG controller 35 maydynamically create a guest instance and then adding a configuration forthe guest instance. That is, for example, NRM 241 may be configured todetermine a capacity and action based on the percentage of usage and, ifthe configured action is to create guest instance, NRM 241 may triggerNICM 245 to create a new instance as described in the following.

Initially, client 258 outputs broadcasts packet and a client subscriberlogin (204). In the example of FIG. 3, vBNG N 257 has an “out ofresources” condition. For example, vBNG N 257 may lack CPU availability,memory, bandwidth, control packet response times, inflight login/logouts(e.g., event rate analyzer), critical management queues, and othersystem resource aspects.

In response to the out of resources condition, vBNG N 257 notifies NRM241 that there are not enough resources (206) and outputs a protocolreject to client 258 (208) and the process proceeds to 214. Saiddifferently, for example, vBNG N 257 may output a notification to NRM241 indicating a lack of computational resources and may output arejection message to client 258. In response, however, to vBNG N 257having sufficient resources, vBNG N 257 may continue the subscriberprotocol negotiation (210).

In response to receiving the notification of insufficient resources, NRM241 outputs, to NLB 247, a notification for recomputing load balancingin response to receiving the notification of insufficient resources. Forinstance, NRM 241 causes NLB 247 to recompute load balancing and outputsa notification to NLB 247 (214).

In response to determining that there are not available vBNG instancesto serve new subscribers, NRM 241 may output, to NICM 245, a request togenerate vBNG M 261 for reducing a load at vBNG N 257. For instance, NRM241 may cause NICM 245 to create vBNG M 261 such that the number ofvBNGs increases by one (218). NICM 245 creates vBNG M 261 (220). NRM 241outputs a request for NLB 247 to recompute load information for vBNG M261 (222). For instance, NRM 241 outputs, to NLB 247, an instruction torecompute load balancing for vBNG M 261. NLB 247 outputs a vBNGsubscriber load balancer credit ‘n’ to vBNG M 261 (226). Client 258outputs a first control negotiation packet to vBNG N 257 (230) and tovBNG M 261 (234).

FIG. 4 is a sequence diagram illustrating an example network loadbalancing process in accordance with techniques described herein. FIG. 4illustrates an example use case describing vBNG advertisement of presentrunning resources local to it and load balancer actions on computing theinputs across vBNG advertising new subscriber credits to vBNG's. FIG. 4is discussed with respect to FIG. 1 and FIG. 2 for exemplary purposesonly. vBNG N 357 may be an example of vBNG N 57N of FIG. 2. vBNG M 361may be an example of vBNG N 61N of FIG. 2. NRM 341 may be an example ofNRM 41 of FIG. 2. NLB 347 may be an example of NLB 47 of FIG. 2. NSDB343 may be an example of NSDB 43 of FIG. 2.

In the example of FIG. 4, when there is too much load of incomingsubscribers or when the incoming subscriber load is out of proportionateacross the instances, there is need to balance the load in order toachieve a higher call setup rate. As such, NLB 347 may maintain creditsor tokens for each of the instances. Such credits or tokens may eachindicate how many incoming subscriber logins a respective BNG instancemay operate. NLB 347 may re-compute the tokens and/or credits based onthe resources and current incoming subscriber rate. NLB 347 may beconfigured with low and high watermarks of a load. Depending upon thewatermarks, NLB 347 may change a number of tokens per instance andpublish to each of the instance. In this way, an instance may allow onlythose many incoming subscriber logins as described in the following.

Initially, every ‘n’ seconds, vBNG N 357 advertises subscriber counts(302). Said differently, for example, vBNG N 357 may periodicallyadvertise subscriber information to NRM 341. In some instances, NRM 341receives, from each vBNG instance of vBNG N 357 and vBNG N 361, arespective subscriber count. NRM 341 updates or modifies a database forvBNG N 357 (304). For instance, NRM 341 modify, for each vBNG instanceof vBNG N 357 and vBNG N 361 a respective entry of NSDB 343 based on therespective subscriber count to generate modified subscriber countinformation. NRM 341 outputs an instruction to NLB 347 to recomputesubscriber load balancer credits (306). Similarly, every ‘n’ seconds,vBNG M 361 advertises subscriber counts (308). In this example, NRM 341updates NSDB 343 for vBNG M 361 (309). In this example, NRM 341 outputsan instruction to NLB 347 to recompute subscriber load balancer credits(310).

NLB 347 recomputes subscriber load balancer credits. More specifically,for example, NLB 347 recomputes vBNG subscriber load balancer creditsfor each vBNG. For instance, NLB 347 recomputes a subscriber loadbalancer credit ‘X’ for vBNG N 357 and recomputes a subscriber loadbalancer credit ‘Y’ for vBNG M 361. In this instance, NLB 347 mayrepublish vBNG subscriber load balancer credits for each vBNG. In thiscase, NLB 347 publishes subscriber load balancer credit ‘X’ to vBNG N357 (312) and publishes subscriber load balancer credit ‘Y’ to vBNG M361 (314). That is, each vBNG instance of vBNG N 357 and vBNG M 361 mayreceive load balancing credit information from NLB 347 and may determinewhether to receive a request to access service provider services basedon the load balancing credit information. NLB 347 outputs load balancercredit history to NRM 341 (316).

FIG. 5 is a sequence diagram illustrating an example dynamic highavailability process in accordance with techniques described herein.FIG. 5 illustrates a use case describing dynamic high availability (DHA)when any vBNG instance is deemed unalive based on heartbeat and health.NRM 441, NICM 445, NLB 447, and NSDB 443 may create a new vBNG instanceand recover all the subscriber and service information corresponding tothe faulty vBNG. NRM 441 may instruct instance manager further to cleanup the faulty vBNG. FIG. 5 is discussed with respect to FIG. 1 and FIG.2 for exemplary purposes only. vBNG 1 457 may be an example of vBNG A57N of FIG. 2. NRM 441 may be an example of NRM 41 of FIG. 2. vBNG N461A may be an example of vBNG A 61N of FIG. 2. NICM 445 may be anexample of NICM 45 of FIG. 2. vBNG N 461N may be an example of vBNG N61N of FIG. 2. NSDB 443 may be an example of NSDB 43 of FIG. 2. NLB 447may be an example of NLB 47 of FIG. 2.

Initially, every ‘n’ seconds, vBNG 1 457 sends heartbeat message to NRM441 (402). Similarly, every ‘n’ seconds, vBNG N 461A sends heartbeatmessage to NRM 441 (404). Said differently, each of vBNG instance ofvBNG 1 457 and vBNG N 461A may periodically output network healthinformation to the BNG controller and NRM 441 may periodically receivehealth data of each vBNG instance of vBNG 1 457 and vBNG N 461A.

However, when vBNG 1 457 does not send a heartbeat message in last ‘n’seconds, NRM 441 outputs a poll vBNG N health message to vBNG 1 457(406). In response to determining that vBNG 1 457 is not present and/orthat there is insufficient health at vBNG 1 457, NRM 441 outputs, toNICM 445, a request to create vBNG N+1 461N (408). Said differently,when health data for vBNG 1 457 is not received within a threshold time,NRM 441 may output, to NICM 445, a request to generate vBNG N+1 461N forrecovering BNG subscriber sessions of vBNG 1 457. NICM 445 creates vBNGN+1 461N (410). NRM 441 outputs, to NSDB 443, an instruction to recovervBNG 1 session previously performed by vBNG 1 457 to vBNG N+1 461N(412). Said differently, NRM 441 may modify an entry of NSDB 443corresponding to vBNG N+1 461N to recover BNG subscriber sessions ofvBNG 1 457. NSDB 443 recovers all sessions previously performed by vBNG1 457 to vBNG N+1 461N (414). For example, a BNG virtual machine manager(e.g., BNG VM manager 59, BNG VM manager 65, etc.) may be configured togenerate vBNG N+1 461N to recreate subscribers replayed (e.g., exact,modified, etc.) subscriber information by NSDB 443 that previouslycorresponded to vBNG 1 457.

NRM 441 outputs, to NICM 445, a request to clean up vBNG 1 457 (416).Said differently, when health data for vBNG 1 457 is not received withinthe threshold time, NRM 441 outputs, to NICM 445, an instruction todestroy vBNG 1 457. NICM 445 outputs, to vBNG 1 457, an instruction todestroy vBNG 1 457 (418). Said differently, NICM 445 outputs aninstruction, to an edge router that provisioned vBNG 1 457, to deletevBNG 1 457 in response to receiving the instruction to destroy vBNG 1457 from NRM 441. In this example, vBNG 1 457 and/or a BNG virtualmachine manager for vBNG 1 457 receives the instruction to destroy vBNG1 457 and destroys the particular vBNG instance.

NRM 441 notifies NLB 447 to recompute the load (420). Said differently,NRM 441 outputs, to NLB 447, an instruction to recompute load balancingfor vBNG N+I 461N. In this example, NLB 447 outputs a load balancercredit to vBNG N+1 461N in response to the instruction to recompute loadbalancing for vBNG N+1 461N. As shown in FIG. 5, when vBNG 1 457 doessend a heartbeat message in last ‘n’ seconds, NRM 441 increments aheartbeat fail count.

FIG. 6 is a flowchart illustrating an example mode of operation of a BNGcontroller in accordance with techniques described herein. FIG. 6 isdiscussed with respect to FIGS. 1-2 for exemplary purposes only.

NSDB 43 stores vBNG instance information for one or more subscriberdevices (500). NICM 45 modifies vBNG instance information to includeadditional vBNG instance to be added to plurality of vBNG instances(502). For example, NRM 41 may output a request to NICM 45 to addadditional vBNG instance. NICM 45 outputs, to edge router 30A,instruction to generate the additional vBNG instance (504). NRM 41outputs, to NLB 47, an instruction to recompute load balancing foradditional vBNG instance (506). NLB 47 outputs a load balancer credit tothe additional vBNG instance (508).

FIG. 7 is a flowchart illustrating an example mode of operation of anedge router in accordance with techniques described herein. FIG. 7 isdiscussed with respect to FIGS. 1-2 for exemplary purposes only.

BNG virtual machine manager 59 receives, from BNG controller 35, aninstruction to generate an additional vBNG instance (600). For example,BNG virtual machine manager 59 receives an instruction to generate vBNGN 57N. BNG virtual machine manager 59 generates the additional vBNGinstance at an edge router to be added to one or more vBNG instances.For example, BNG virtual machine manager 59 generates vBNG N 57N at edgerouter 30 to be added to vBNG N 57A-vBNG N 57M (not shown).

BNG instances 57 receive a request to access service provider servicesfrom one or more subscriber devices (604). For example, vBNG instances57 receive requests to access service provider network 20 fromsubscriber devices 18. vBNG instances 57 selectively authenticaterespective requests to access service provider services (606).

The techniques described herein may be implemented in hardware,software, firmware, or any combination thereof, in private or publiccloud or standalone application, all the applications could beincorporated as one single application suite or different applicationsdistributed in the network or at a centralized node. Various featuresdescribed as modules, units or components may be implemented together inan integrated logic device or separately as discrete but interoperablelogic devices or other hardware devices. In some cases, various featuresof electronic circuitry may be implemented as one or more integratedcircuit devices, such as an integrated circuit chip or chipset.

If implemented in hardware, this disclosure may be directed to anapparatus such a processor or an integrated circuit device, such as anintegrated circuit chip or chipset. Alternatively or additionally, ifimplemented in software or firmware, the techniques may be realized atleast in part by a computer-readable data storage medium comprisinginstructions that, when executed, cause a processor to perform one ormore of the methods described above. For example, the computer-readabledata storage medium may store such instructions for execution by aprocessor.

A computer-readable medium or computer-readable storage device may formpart of a computer program product, which may include packagingmaterials. A computer-readable medium may comprise a computer datastorage medium such as random access memory (RAM), read-only memory(ROM), non-volatile random access memory (NVRAM), electrically erasableprogrammable read-only memory (EEPROM), Flash memory, magnetic oroptical data storage media, and the like. In some examples, an articleof manufacture may comprise one or more computer-readable storage media.

In some examples, the computer-readable storage media may comprisenon-transitory media. The term “non-transitory” may indicate that thestorage medium is not embodied in a carrier wave or a propagated signal.In certain examples, a non-transitory storage medium may store data thatcan, over time, change (e.g., in RAM or cache).

The code or instructions may be software and/or firmware executed byprocessing circuitry including one or more processors, such as one ormore digital signal processors (DSPs), general purpose microprocessors,application-specific integrated circuits (ASICs), field-programmablegate arrays (FPGAs), or other equivalent integrated or discrete logiccircuitry. Accordingly, the term “processor,” as used herein may referto any of the foregoing structure or any other structure suitable forimplementation of the techniques described herein. In addition, in someaspects, functionality described in this disclosure may be providedwithin software modules or hardware modules.

In addition to or as an alternative to the above, the following examplesare described. The features described in any of the following examplesmay be utilized with any of the other examples described herein.

Example 1

A broadband network gateway (BNG) controller that manages virtual BNG(vBNG) instances, the BNG controller comprising: a memory; one or moreprocessors in communication with the memory; a network subscriberdatabase (NSDB) configured to store vBNG instance information for one ormore subscriber devices, the vBNG instance information specifying aplurality of vBNG instances operable by one or more edge routers,wherein the plurality of vBNG instances are configured to receiverequests to access service provider services from the one or moresubscriber devices and to selectively authenticate the one or moresubscriber devices for network services based on authenticationinformation included in the requests to access services providerservices; and one or more core applications operable by the one or moreprocessors, wherein the one or more core applications include a networkinstance and configuration manager (NICM) configured to modify the vBNGinstance information to include an additional vBNG instance to be addedto the plurality of vBNG instances and to output, to an edge router ofthe one or more edge routers, an instruction to generate the additionalvBNG instance at the edge router.

Example 2

The BNG controller of example 1, wherein the NICM is further configuredto: receive one or more configuration updates; and output aconfiguration template specifying the one or more configuration updatesto update each vBNG instance of the plurality of vBNG instances.

Example 3

The BNG controller of any combination of examples 1-2, wherein the oneor more core applications include a network resource manager (NRM)configured to: receive a notification of insufficient resources from aparticular vBNG instance of the plurality of vBNG instances; and output,to the NICM, a request to generate the additional vBNG instance forreducing a load at the particular vBNG instance in response to receivingthe notification of insufficient resources, wherein the NICM isconfigured to output the instruction to generate the additional vBNGinstance in response to the request to generate the additional vBNGinstance.

Example 4

The BNG controller of example 3, wherein the one or more coreapplications include a network load balancer (NLB) configured to loadbalance the plurality of vBNG instances based on the vBNG instanceinformation and wherein the NRM is further configured to: output, to theNLB, a notification for recomputing load balancing in response toreceiving the notification of insufficient resources; and output, to theNLB, an instruction to recompute load balancing for the additional vBNGinstance, wherein the NLB outputs a load balancer credit to theadditional vBNG instance in response to the instruction to recomputeload balancing for the additional vBNG instance.

Example 5

The BNG controller of any combination of examples 1-2, wherein the oneor more core applications include a network load balancer (NLB)configured to load balance the plurality of vBNG instances based on thevBNG instance information and a network resource manager (NRM)configured to: receive, from each vBNG instance of the plurality of vBNGinstances, a respective subscriber count or a respective inflightinformation count; and modify, for each vBNG instance of the pluralityof vBNG instances, a respective entry of the NSDB based on therespective subscriber count or the respective inflight information countto generate modified subscriber information, wherein the NLB isconfigured to: recompute, for each vBNG instance of the plurality ofvBNG instances, a subscriber load balancer credit based on the modifiedsubscriber information; output, to each vBNG instance of the pluralityof vBNG instances, a respective subscriber load balancer credit; andoutput a load balancer credit history to the NRM, the load balancercredit history being generated based on each respective subscriber loadbalancer credit.

Example 6

The BNG controller of any combination of examples 1-2, wherein the oneor more core applications include a network resource manager (NRM)configured to: periodically receive health data of each vBNG instance ofthe plurality of vBNG instances; and when health data for a particularvBNG instance of the plurality of vBNG instances is not received withina threshold time, output, to the NICM, a request to generate theadditional vBNG instance for recovering BNG subscriber sessions of theparticular vBNG instance from the NSDB, wherein the NICM is configuredto output the instruction to generate the additional vBNG instance inresponse to the request to generate the additional vBNG instance and torecover the BNG subscriber sessions of the particular vBNG instance fromthe NSDB.

Example 7

The BNG controller of example 6, wherein the NRM is configured to: whenhealth data for the particular vBNG instance of the plurality of vBNGinstances is not received within the threshold time, output, to theNICM, an instruction to destroy the particular vBNG instance, whereinthe NICM is further configured to output an instruction, to edge routerof the one or more edge routers that provisioned the particular vBNGinstance, to delete the particular vBNG instance in response toreceiving the instruction to destroy the particular vBNG instance.

Example 8

The BNG controller of any combination of examples 6-7, wherein the oneor more core applications include a network load balancer (NLB)configured to load balance the plurality of vBNG instances based on thevBNG instance information and wherein the NRM is further configured to:modify an entry of the NSDB corresponding to the additional vBNGinstance to recover BNG subscriber sessions of the particular vBNGinstance; and output, to the NLB, an instruction to recompute loadbalancing for the additional vBNG instance, wherein the NLB outputs aload balancer credit to the additional vBNG instance in response to theinstruction to recompute load balancing for the additional vBNGinstance.

Example 9

The BNG controller of any combination of examples 1-8, wherein the NSDBincludes subscriber colocation information and BNG specific information.

Example 10

The BNG controller of any combination of examples 1-9, wherein the oneor more core applications include subscriber analytics (SA) configuredto: receive analytics data from at least one of the plurality of vBNGinstances; and generate subscriber behavior data based on the analyticsdata for operating the plurality of vBNG instances.

Example 11

The BNG controller of any combination of examples 1-10, wherein the oneor more core applications include unified network security management(UNSM) configured to: receive network security data from the pluralityof vBNG instances; analyze the received network security data togenerate one or more alerts; output the one or more alerts; andconfigure, with the NICM, the plurality of vBNG instances based on thenetwork security data.

Example 12

The BNG controller of any combination of examples 1-11, wherein the oneor more core applications include dynamic high availability (DHA)configured to: dynamically spawn an additional vBNG instance to providehigh availability to an existing vBNG instance of the plurality of vBNGinstances, based on a configuration policy; and dynamically collapse oneor more vBNG instances which were providing high availability, based onthe configuration policy.

Example 13

The BNG controller of any combination of examples 1-12, wherein the BNGcontroller that manages the vBNG instances further manages one or morephysical BNGs and wherein each physical BNG of the one or more physicalBNGs is configured to manage subscriber management centrally.

Example 14

The BNG controller of any combination of examples 1-13, wherein the oneor more core applications are executed at a centralized computing deviceor executed at a plurality of networked computing elements distributedin a cloud configuration.

Example 15

A method for managing subscriber logins for network subscribers, themethod comprising: storing, by a network subscriber database (NSDB) of abroadband network gateway (BNG) controller, vBNG instance informationfor one or more subscriber devices, the vBNG instance informationspecifying a plurality of vBNG instances operable by one or more edgerouters, wherein the plurality of vBNG instances are configured toreceive requests to access service provider services from the one ormore subscriber devices and to selectively authenticate the one or moresubscriber devices based on authentication information included in therequests to access services provider services; modifying, by a networkinstance and configuration manager (NICM) operable by one or moreprocessors of the BNG controller, the vBNG instance information toinclude an additional vBNG instance to be added to the plurality of vBNGinstances; and outputting, by the NICM, to an edge router of the one ormore edge routers, an instruction to generate the additional vBNGinstance at the edge router.

Example 16

The method of example 15, further comprising: receiving, by a networkresource manager (NRM) operable by the one or more processors, anotification of insufficient resources from a particular vBNG instanceof the plurality of vBNG instances; outputting, by the NRM, to the NICM,a request to generate the additional vBNG instance for reducing a loadat the particular vBNG instance in response to receiving thenotification of insufficient resources, wherein outputting theinstruction to generate the additional vBNG instance is in response tothe request to generate the additional vBNG instance.

Example 17

The method of example 16, further comprising: outputting, by the NRM, toa network load balancer (NLB) operable by the one or more processors, anotification for recomputing load balancing in response to receiving thenotification of insufficient resources; outputting, by the NRM, to theNLB, an instruction to recompute load balancing for the additional vBNGinstance; and outputting, by the NLB, a load balancer credit to theadditional vBNG instance in response to the instruction to recomputeload balancing for the additional vBNG instance.

Example 18

The method of example 15, further comprising: receiving, by a networkresource manager (NRM) operable by the one or more processors, from eachvBNG instance of the plurality of vBNG instances, a respectivesubscriber count; modifying, by the NRM, for each vBNG instance of theplurality of vBNG instances, a respective entry of the NSDB based on therespective subscriber count to generate modified subscriber countinformation; recomputing, by network load balancer (NLB) operable by theone or more processors, for each vBNG instance of the plurality of vBNGinstances, a subscriber load balancer credit based on the modifiedsubscriber count information; outputting, by the NLB, to each vBNGinstance of the plurality of vBNG instances, a respective subscriberload balancer credit; and outputting, by the NLB, a load balancer credithistory to the NRM, the load balancer credit history being generatedbased on each respective subscriber load balancer credit.

Example 19

The method of example 15, further comprising: periodically receivinghealth data of each vBNG instance of the plurality of vBNG instances;when health data for a particular vBNG instance of the plurality of vBNGinstances is not received within a threshold time, outputting, by anetwork resource manager (NRM) operable by the one or more processors,to the NICM, a request to generate the additional vBNG instance forrecovering BNG subscriber sessions of the particular vBNG instance,wherein outputting the instruction to generate the additional vBNGinstance is in response to the instruction to create the additional vBNGinstance and wherein modifying the vBNG instance information comprisesrecovering the BNG subscriber sessions of the particular vBNG instancefrom the NSDB.

Example 20

The method of example 19, further comprising: when health data for theparticular vBNG instance of the plurality of vBNG instances is notreceived within the threshold time, outputting, by the NRM, to the NICM,an instruction to destroy the particular vBNG instance; and outputting,by the NICM, to an edge router of the one or more edge routers thatprovisioned the particular instance, an instruction to delete theparticular vBNG instance in response to receiving the instruction todestroy the particular vBNG instance.

Example 21

The method of any combination of examples 19-20, further comprising:modifying, by the NRM, an entry of the NSDB corresponding to theadditional vBNG instance to recover BNG subscriber sessions of theparticular vBNG instance; and outputting, by the NRM, to a network loadbalancer (NLB) operable by the one or more processors, an instruction torecompute load balancing for the additional vBNG instance; andoutputting, by the NLB, a load balancer credit to the additional vBNGinstance in response to the instruction to recompute load balancing forthe additional vBNG instance.

Example 22

An edge router comprising: a memory; one or more processors incommunication with the memory; a broadband network gateway (BNG) virtualmachine manager operable by the one or more processors and configured toreceive, from a BNG controller, an instruction to generate a virtual BNG(vBNG) instance and, in response to the instruction, generate the vBNGinstance to provision one or more vBNG instances at the edge router; andone or more vBNG instances operable by the one or more processors andconfigured to receive a request to access service provider services fromone or more subscriber devices, and selectively authenticate the one ormore subscriber devices based on authentication information included inthe requests to access services provider services.

Example 23

The edge router of example 22, wherein each vBNG instance of the one ormore vBNG instances is further configured to: in response to determiningthat the vBNG instance does not have enough computational resources toprocess a subscriber login from a subscriber device of the one or moresubscriber devices: output a notification to the BNG controllerindicating a lack of computational resources; and output a rejectionmessage to the subscriber device.

Example 24

The edge router of any combination of examples 22-23, wherein each vBNGinstance of the one or more vBNG instances is further configured to:periodically advertise subscriber information to the BNG controller; andreceive load balancing credit information from the BNG controller,wherein each vBNG instance of the one or more vBNG instances isconfigured to determine whether to receive the request to access serviceprovider services based on the load balancing credit information.

Example 25

The edge router of any combination of examples 22-24, wherein each vBNGinstance of the one or more vBNG instances is further configured to:periodically output network health information to the BNG controller.

Example 26

The edge router of any combination of examples 22-25, wherein each vBNGinstance of the one or more vBNG instances is further configured to:receive configuration updates from a network instance and configurationmanager (NICM) of the BNG controller; exchange security relatedinformation with the NICM of the BNG controller; receive updates from aunified network security management (UNSM) of the BNG controller;receive load balancing credit information from the BNG controller; orsynchronize a local database with a network subscriber database (NSDB)of the BNG controller.

Example 27

The edge router of any combination of examples 22-25, wherein, togenerate the vBNG instance, the BNG virtual machine manager isconfigured to generate the vBNG instance to recreate replayed subscriberinformation by a network subscriber database (NSDB) of the BNGcontroller.

Example 28

The edge router of any combination of examples 22-27, wherein the BNGvirtual machine manager is further configured to: receive, from the BNGcontroller, an instruction to destroy a particular vBNG instance of theone or more vBNG instances; and destroy the particular vBNG instance inresponse to the instruction to destroy the particular vBNG instance.

Example 29

A method comprising: receiving, by a broadband network gateway (BNG)virtual machine manager operable by one or more processors of an edgerouter, from a BNG controller, an instruction to generate a virtual BNG(vBNG) instance; and generating, by the BNG virtual machine manager, thevBNG instance at the edge router to provision one or more vBNG instancesoperable by the one or more processors in response to the instruction;receiving, by the one or more vBNG instances operable by the one or moreprocessors, a request to access service provider services from one ormore subscriber devices; and selectively authenticating, by the one ormore vBNG instances, the one or more subscriber devices based onauthentication information included in the requests to access servicesprovider services.

Example 30

The method of example 29, further comprising: in response todetermining, by a particular vBNG instance of the one or more vBNGinstances, that the vBNG instance does not have enough computationalresources to process a subscriber login from a subscriber device of theone or more subscriber devices: outputting, by the particular vBNGinstance, a notification to the BNG controller indicating a lack ofcomputational resources; and outputting, by the particular vBNGinstance, a rejection message to the subscriber device.

Example 31

The method of any combination of examples 29-30, further comprising:periodically advertising, by each vBNG instance of the one or more vBNGinstances, subscriber information to the BNG controller; receiving, byeach vBNG instance of the one or more vBNG instances, load balancingcredit information from the BNG controller; and determining, by eachvBNG instance of the one or more vBNG instances, whether to receive therequest to access service provider services based on the load balancingcredit information.

Example 32

The method of any combination of examples 29-31, further comprising:periodically outputting, by each vBNG instance of the one or more vBNGinstances, network health information to the BNG controller.

Example 33

The method of any combination of examples 29-32, further comprising:receiving, by the BNG virtual machine manager, from the BNG controller,an instruction to destroy a particular vBNG instance of the one or morevBNG instances; and destroying, by the BNG virtual machine manager, theparticular vBNG instance in response to the instruction to destroy theparticular vBNG instance.

Example 34

The method of any combination of examples 29-33, wherein each vBNGinstance of the one or more vBNG instances is further configured to:receive configuration updates from a network instance and configurationmanager (NICM) of the BNG controller; exchange security relatedinformation with the NICM; receive updates from a unified networksecurity management (UNSM) of the BNG controller; receive load balancingcredit information from a network load balancer (NLB) of the BNGcontroller; or synchronize a local database with a network subscriberdatabase (NSDB) of the BNG controller.

Example 35

The method of any combination of examples 29-33, wherein generating thevBNG instance comprises generating the vBNG instance to recreatereplayed subscriber information by a network subscriber database (NSDB)of the BNG controller.

Example 36

The method of any combination of examples 29-35, wherein each vBNGinstance of the one or more vBNG instances is further configured to:receive a configuration template specifying one or more configurationupdates; and apply the configuration template to implement the one ormore configuration updates.

Moreover, any of the specific features set forth in any of the examplesdescribed above may be combined into beneficial examples of thedescribed techniques. That is, any of the specific features aregenerally applicable to all examples of the invention. Variousembodiments have been described. These and other embodiments are withinthe scope of the following examples.

What is claimed is:
 1. A broadband network gateway (BNG) controller thatmanages virtual BNG (vBNG) instances, the BNG controller comprising: amemory; one or more processors in communication with the memory; anetwork subscriber database (NSDB) configured to store vBNG instanceinformation for one or more subscriber devices, the vBNG instanceinformation specifying a plurality of vBNG instances operable by one ormore edge routers, wherein the plurality of vBNG instances areconfigured to receive requests to access service provider services fromthe one or more subscriber devices and to selectively authenticate theone or more subscriber devices for network services based onauthentication information included in the requests to access servicesprovider services; and one or more core applications operable by the oneor more processors, wherein the one or more core applications include anetwork instance and configuration manager (NICM) configured to modifythe vBNG instance information to include an additional vBNG instance tobe added to the plurality of vBNG instances and to output, to an edgerouter of the one or more edge routers, an instruction to generate theadditional vBNG instance at the edge router.
 2. The BNG controller ofclaim 1, wherein the one or more core applications include a networkresource manager (NRM) configured to: receive a notification ofinsufficient resources from a particular vBNG instance of the pluralityof vBNG instances; and output, to the NICM, a request to generate theadditional vBNG instance for reducing a load at the particular vBNGinstance in response to receiving the notification of insufficientresources, wherein the NICM is configured to output the instruction togenerate the additional vBNG instance in response to the request togenerate the additional vBNG instance.
 3. The BNG controller of claim 3,wherein the one or more core applications include a network loadbalancer (NLB) configured to load balance the plurality of vBNGinstances based on the vBNG instance information and wherein the NRM isfurther configured to: output, to the NLB, a notification forrecomputing load balancing in response to receiving the notification ofinsufficient resources; and output, to the NLB, an instruction torecompute load balancing for the additional vBNG instance, wherein theNLB outputs a load balancer credit to the additional vBNG instance inresponse to the instruction to recompute load balancing for theadditional vBNG instance.
 4. The BNG controller of claim 1, wherein theone or more core applications include a network load balancer (NLB)configured to load balance the plurality of vBNG instances based on thevBNG instance information and a network resource manager (NRM)configured to: receive, from each vBNG instance of the plurality of vBNGinstances, a respective subscriber count or a respective inflightinformation count; and modify, for each vBNG instance of the pluralityof vBNG instances, a respective entry of the NSDB based on therespective subscriber count or the respective inflight information countto generate modified subscriber information, wherein the NLB isconfigured to: recompute, for each vBNG instance of the plurality ofvBNG instances, a subscriber load balancer credit based on the modifiedsubscriber information; output, to each vBNG instance of the pluralityof vBNG instances, a respective subscriber load balancer credit; andoutput a load balancer credit history to the NRM, the load balancercredit history being generated based on each respective subscriber loadbalancer credit.
 5. The BNG controller of claim 1, wherein the NSDBincludes subscriber colocation information and BNG specific information.6. The BNG controller of claim 1, wherein the one or more coreapplications include dynamic high availability (DHA) configured to:dynamically spawn an additional vBNG instance to provide highavailability to an existing vBNG instance of the plurality of vBNGinstances, based on a configuration policy; and dynamically collapse oneor more vBNG instances which were providing high availability, based onthe configuration policy.
 7. The BNG controller of claim 1, wherein theone or more core applications are executed at a centralized computingdevice or executed at a plurality of networked computing elementsdistributed in a cloud configuration.
 8. A method for managingsubscriber logins for network subscribers, the method comprising:storing, by a network subscriber database (NSDB) of a broadband networkgateway (BNG) controller, vBNG instance information for one or moresubscriber devices, the vBNG instance information specifying a pluralityof vBNG instances operable by one or more edge routers, wherein theplurality of vBNG instances are configured to receive requests to accessservice provider services from the one or more subscriber devices and toselectively authenticate the one or more subscriber devices based onauthentication information included in the requests to access servicesprovider services; modifying, by a network instance and configurationmanager (NICM) operable by one or more processors of the BNG controller,the vBNG instance information to include an additional vBNG instance tobe added to the plurality of vBNG instances; and outputting, by theNICM, to an edge router of the one or more edge routers, an instructionto generate the additional vBNG instance at the edge router.
 9. Themethod of claim 8, further comprising: receiving, by a network resourcemanager (NRM) operable by the one or more processors, a notification ofinsufficient resources from a particular vBNG instance of the pluralityof vBNG instances; outputting, by the NRM, to the NICM, a request togenerate the additional vBNG instance for reducing a load at theparticular vBNG instance in response to receiving the notification ofinsufficient resources, wherein outputting the instruction to generatethe additional vBNG instance is in response to the request to generatethe additional vBNG instance.
 10. The method of claim 9, furthercomprising: outputting, by the NRM, to a network load balancer (NLB)operable by the one or more processors, a notification for recomputingload balancing in response to receiving the notification of insufficientresources; outputting, by the NRM, to the NLB, an instruction torecompute load balancing for the additional vBNG instance; andoutputting, by the NLB, a load balancer credit to the additional vBNGinstance in response to the instruction to recompute load balancing forthe additional vBNG instance.
 11. The method of claim 8, furthercomprising: receiving, by a network resource manager (NRM) operable bythe one or more processors, from each vBNG instance of the plurality ofvBNG instances, a respective subscriber count; modifying, by the NRM,for each vBNG instance of the plurality of vBNG instances, a respectiveentry of the NSDB based on the respective subscriber count to generatemodified subscriber count information; recomputing, by network loadbalancer (NLB) operable by the one or more processors, for each vBNGinstance of the plurality of vBNG instances, a subscriber load balancercredit based on the modified subscriber count information; outputting,by the NLB, to each vBNG instance of the plurality of vBNG instances, arespective subscriber load balancer credit; and outputting, by the NLB,a load balancer credit history to the NRM, the load balancer credithistory being generated based on each respective subscriber loadbalancer credit.
 12. An edge router comprising: a memory; one or moreprocessors in communication with the memory; a broadband network gateway(BNG) virtual machine manager operable by the one or more processors andconfigured to receive, from a BNG controller, an instruction to generatea virtual BNG (vBNG) instance and, in response to the instruction,generate the vBNG instance to provision one or more vBNG instances atthe edge router; and one or more vBNG instances operable by the one ormore processors and configured to receive a request to access serviceprovider services from one or more subscriber devices, and selectivelyauthenticate the one or more subscriber devices based on authenticationinformation included in the requests to access services providerservices.
 13. The edge router of claim 12, wherein the BNG virtualmachine manager is further configured to: receive, from the BNGcontroller, an instruction to destroy a particular vBNG instance of theone or more vBNG instances; and destroy the particular vBNG instance inresponse to the instruction to destroy the particular vBNG instance.